This PR is supposed to help with the issue that is described in emberjs/ember-render-modifiers#64

Essentially npm thinks that ranges shouldn't be satisfied if you are using pre-releases. You can overcome this if you use an overrides in npm which works in a very similar way to yarn resolutions.

The issue is that if you provide an overrides config to ember-try it will just ignore it:

{
  name: 'ember-release',
  npm: {
    devDependencies: {
      'ember-source': await getChannelURL('release'),
    },
    overrides: {
      'ember-source': '$ember-source',
    },
  },
},

This PR implements npm overrides in much the same way as yarn resolutions 👍 in fact I copy and pasted all of the resolutions tests and just changed resolutions to overrides in most cases 😂